We should use structured errors with field errors so that all errors are returned to the client instead of only validating part of the error.

Let's use the name ResourceSearchQuery so it's a little more unique to what we're searching. This gives us flexibility to have other types of search queries in the future that won't conflict with this type.

We'll want to investigate if there's a better way to embed a resource here. I believe this would result in a raw JSON object which is not ideal.

After investigation, unstructured.Unstructured is the better choice here over runtime.RawExtension.

Why Unstructured:

• Provides typed accessor methods for Go clients (GetName(), GetNamespace(), GetLabels(), etc.) without requiring manual JSON parsing
• Implements runtime.Object, so it works directly with dynamic clients and controller-runtime machinery
• Wire format is identical to RawExtension—non-Go clients see the same JSON, so this is backward compatible

Why not RawExtension:

• Clients must manually unmarshal and type-assert fields
• No benefit over Unstructured since we are not doing raw byte pass-through

Alternative considered:
We could extract common fields (apiVersion, kind, name, namespace) into explicit struct fields for maximum ergonomics, but Unstructured provides a good balance without duplicating data in the response.

type SearchResult struct {
    Resource       unstructured.Unstructured `json:"resource"`
    RelevanceScore float64                   `json:"relevanceScore,omitempty"`
}